-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added a template for an issue created for a FLIP #127
Conversation
The new FLIP process additionally requires an issue to be created
* be civil and constructive (see [Code of Conduct](CODE_OF_CONDUCT.md)) | ||
* Provide feedback as soon as possible to allow adequate time for consideration | ||
* Read FLIPs thoroughly before providing feedback | ||
* Be civil and constructive (see [Code of Conduct](CODE_OF_CONDUCT.md)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link to the Code of Conduct doesn't open - should be removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link should not be removed, instead, the missing Code of Conduct should be added to the repo: https://github.com/onflow/flow/blob/master/CODE_OF_CONDUCT.md
README.md
Outdated
|
||
Note the issue number that gets assigned e.g. for issue https://github.com/onflow/flips/issues/76 the issue number is `76`. | ||
|
||
4. Create your FLIP as a pull request to this repository ([`onflow/flips`](https://github.com/onflow/flips)). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this step can we add a reminder to link the PR(s) to the issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah - i did mentioned - "Mention the FLIP issue by copying the GitHub URL or the issue in the comment section." lemme know if that will suffice.
Adding instruction to mention the issue in the PR
removing the use of label on issue to track status.
Adding Drafted status
TODO:
|
Co-authored-by: Bastian Müller <[email protected]>
Co-authored-by: Bastian Müller <[email protected]>
Co-authored-by: Bastian Müller <[email protected]>
Co-authored-by: Bastian Müller <[email protected]>
Co-authored-by: Bastian Müller <[email protected]>
Co-authored-by: Bastian Müller <[email protected]>
Co-authored-by: Bastian Müller <[email protected]>
hey folks - I have update the PR to include separate issue templates for each of the 4 FLIP type - cadence, application, protocol and governance so that whenever a user creates an issue, the label for the issue type gets automatically applied. |
No description provided.